Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1879

reference
51-tree-1
name
1879
tree-preservation-order

undefined

51-tpo-1
uprn
address-text
point
POINT (-1.001370 50.794422)
geometry
MULTIPOLYGON (((-1.001313 50.794416,-1.001316 50.794427,-1.001324 50.794438,-1.001336 50.794446,-1.001352 50.794451,-1.001369 50.794453,-1.001387 50.794451,-1.001403 50.794446,-1.001416 50.794438,-1.001424 50.794428,-1.001427 50.794417,-1.001424 50.794406,-1.001417 50.794396,-1.001404 50.794388,-1.001388 50.794383,-1.001371 50.794381,-1.001353 50.794382,-1.001337 50.794387,-1.001325 50.794395,-1.001316 50.794405,-1.001313 50.794416)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL